Triple
T31504104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Imperial City |
E803769
|
entity |
| Predicate | owesFealtyDirectlyTo |
P7255
|
FINISHED |
| Object | emperor |
—
|
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: emperor | Statement: [Free Imperial City, owesFealtyDirectlyTo, emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: owesFealtyDirectlyTo Context triple: [Free Imperial City, owesFealtyDirectlyTo, emperor]
-
A.
vassalsOf
chosen
Indicates that one entity serves as a subordinate or dependent vassal under the authority or suzerainty of another entity.
-
B.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
-
C.
relationshipToOverlords
Indicates the nature or type of connection, role, or allegiance that an entity has in relation to its overlords.
-
D.
associatedWithDynastyOrFaction
Indicates that an entity is linked to, belongs to, or is significantly connected with a particular dynasty or faction.
-
E.
followsLeadershipOf
Indicates that one entity accepts and acts under the guidance, direction, or authority of another entity’s leadership.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a214a24481908d30547f6d36aabe |
completed | May 3, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:46 p.m.