Triple
T15860722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTL* |
E384578
|
entity |
| Predicate | hasTemporalOperator |
P120796
|
FINISHED |
| Object | X |
—
|
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: X | Statement: [CTL*, hasTemporalOperator, X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalOperator Context triple: [CTL*, hasTemporalOperator, X]
-
A.
hasTemporalBehavior
Indicates that an entity exhibits a particular pattern, characteristic, or change in behavior over time.
-
B.
hasTemporalAttribute
Indicates that an entity is associated with a specific temporal property or characteristic, such as time, duration, or period.
-
C.
hasHistoricalOperator
Indicates that an entity is or has been managed, controlled, or operated by a specific operator at some point in the past.
-
D.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
-
E.
hasTemporalRole
Indicates that an entity participates in a role or function that is defined, constrained, or characterized by a specific time or temporal context.
- F. None of above. chosen
Provenance (4 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.