Triple
T5425663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E(n) |
E121355
|
entity |
| Predicate | hasGroupOperation |
P55691
|
FINISHED |
| Object | composition of transformations |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: composition of transformations | Statement: [E(n), hasGroupOperation, composition of transformations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroupOperation Context triple: [E(n), hasGroupOperation, composition of transformations]
-
A.
hasGlobalOperationsIn
Indicates that an entity conducts business or operational activities across multiple countries within the specified region or location.
-
B.
hasGlobalOperations
Indicates that an entity conducts its activities or services across multiple countries or worldwide.
-
C.
hasPostgroupOperator
chosen
Indicates that one entity is associated with an operator that is applied after a primary operation or grouping has been performed on another entity.
-
D.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
E.
hasBusinessOperation
Indicates that one entity conducts, manages, or is engaged in a commercial or organizational activity involving another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.