Triple
T38690344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Constantinople (378) |
E949242
|
entity |
| Predicate | capitalUnderThreat |
P174589
|
FINISHED |
| Object | Constantinople |
—
|
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: Constantinople | Statement: [Battle of Constantinople (378), capitalUnderThreat, Constantinople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalUnderThreat Context triple: [Battle of Constantinople (378), capitalUnderThreat, Constantinople]
-
A.
collectiveThreat
Indicates a situation where multiple entities together pose or experience a shared threat as a unified group rather than as isolated individuals.
-
B.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
threatenedIn
chosen
Indicates that one entity is under threat, danger, or risk within the context, location, or situation specified by another entity.
-
D.
threatsFaced
Indicates that an entity is exposed to or experiences specific dangers, risks, or harmful conditions.
-
E.
hasDestructibleCities
Indicates that the subject possesses or includes cities that are capable of being destroyed.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 3, 2026, 4:33 p.m.