Triple
T33030149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillaume d’Orange epic cycle |
E845141
|
entity |
| Predicate | heroTitle |
P90821
|
FINISHED |
| Object | count of Orange |
—
|
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: count of Orange | Statement: [Guillaume d’Orange epic cycle, heroTitle, count of Orange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroTitle Context triple: [Guillaume d’Orange epic cycle, heroTitle, count of Orange]
-
A.
hasHeroTitle
Indicates that an entity holds or is assigned a specific heroic title or designation.
-
B.
characterTitle
chosen
Indicates that a character holds or is associated with a specific title, rank, or formal designation.
-
C.
protagonistTitle
Indicates that one entity is the title or designation held by the main or central character (protagonist) of a work or narrative.
-
D.
heroClass
Indicates the character class or role that a hero belongs to within a given system or context.
-
E.
heroDepicted
Indicates that one entity is portrayed or represented as a hero in relation to 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.