Triple
T31117406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsstädte |
E793127
|
entity |
| Predicate | wereOrganizedIn |
P8619
|
FINISHED |
| Object | College of Imperial Cities |
—
|
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: College of Imperial Cities | Statement: [Reichsstädte, wereOrganizedIn, College of Imperial Cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereOrganizedIn Context triple: [Reichsstädte, wereOrganizedIn, College of Imperial Cities]
-
A.
organisedIn
chosen
Indicates that an event, activity, or entity is arranged, coordinated, or held within a particular place, context, or organizational framework.
-
B.
areOrganizedBy
Indicates that one entity is responsible for planning, coordinating, or managing the structure or execution of another entity or event.
-
C.
organisedDuring
Indicates that an organizing action or arrangement took place within the time span of a specified event or period.
-
D.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
E.
organisedWith
Indicates that two or more entities are arranged, coordinated, or structured together as part of the same organizing context or effort.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:04 p.m.