Triple
T31117426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsstädte |
E793127
|
entity |
| Predicate | includedExample |
P100896
|
FINISHED |
| Object | Free Imperial City of Nuremberg |
—
|
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: Free Imperial City of Nuremberg | Statement: [Reichsstädte, includedExample, Free Imperial City of Nuremberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedExample Context triple: [Reichsstädte, includedExample, Free Imperial City of Nuremberg]
-
A.
includesExamplesSuchAs
chosen
Indicates that one entity provides specific instances or samples that illustrate or clarify another entity.
-
B.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
includedSingle
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
-
E.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
- 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_6a00be8ee4bc8190b795d9606f0e490c |
completed | May 10, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_6a00bde163c88190867104bd08cac2ee |
completed | May 10, 2026, 5:18 p.m. |
Created at: April 29, 2026, 9:04 p.m.