Triple
T7280683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippodrome of Constantinople |
E163136
|
entity |
| Predicate | plunderedIn |
P16501
|
FINISHED |
| Object | 1204 |
—
|
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: 1204 | Statement: [Hippodrome of Constantinople, plunderedIn, 1204]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plunderedIn Context triple: [Hippodrome of Constantinople, plunderedIn, 1204]
-
A.
lootedBy
chosen
Indicates that something has been forcibly taken or plundered by a specified agent or group.
-
B.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
C.
excavatedIn
Indicates that something (typically an artifact, structure, or site) was uncovered or dug out during an excavation that took place at a specific time or within a specific time period.
-
D.
conqueredInPartBy
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
-
E.
surrenderedIn
Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb34fe0c8190a642fd3339f0cacd |
completed | March 27, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.