Triple
T19921306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line (Cyprus) |
E478800
|
entity |
| Predicate | maintainedSince |
P137832
|
FINISHED |
| Object | 1974 ceasefire |
—
|
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: 1974 ceasefire | Statement: [Green Line (Cyprus), maintainedSince, 1974 ceasefire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedSince Context triple: [Green Line (Cyprus), maintainedSince, 1974 ceasefire]
-
A.
maintainedAt
Indicates that an entity is kept in proper working order, condition, or status at a particular place, time, or context.
-
B.
maintainedFor
Indicates that something is kept in a particular state, condition, or operation for the benefit, use, or purpose of another entity.
-
C.
maintainedDuring
Indicates that a certain condition, state, or relationship continues to hold throughout the duration of a specified event or time interval.
-
D.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
E.
maintainedWithin
Indicates that one entity is kept, preserved, or sustained inside the boundaries or context of another entity.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c564788190a3893fc73fc4922b |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.