Triple
T35568426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemnos, Imbros, and Scyros to belong to Athens |
E1027842
|
entity |
| Predicate | confirmsControlOf |
P29286
|
FINISHED |
| Object | Lemnos |
—
|
NE NERFINISHED |
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: Lemnos | Statement: [Lemnos, Imbros, and Scyros to belong to Athens, confirmsControlOf, Lemnos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmsControlOf Context triple: [Lemnos, Imbros, and Scyros to belong to Athens, confirmsControlOf, Lemnos]
-
A.
recognizedControlOf
chosen
Indicates that one entity has formally acknowledged and accepted another entity’s authority or control over something.
-
B.
exertsControlOver
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of another entity.
-
C.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
D.
controlsOrControlled
Indicates that one entity has control over another entity or is itself under the control of that other entity.
-
E.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.