Triple
T36603221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Marquis de las Cisternas |
E902973
|
entity |
| Predicate | isFictionalNobleRank |
P117060
|
FINISHED |
| Object | Marquis |
—
|
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: Marquis | Statement: [The Marquis de las Cisternas, isFictionalNobleRank, Marquis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFictionalNobleRank Context triple: [The Marquis de las Cisternas, isFictionalNobleRank, Marquis]
-
A.
isFictionalAristocratIn
Indicates that a character is a fictional member of the aristocracy who appears in or belongs to a specified work, setting, or universe.
-
B.
isFictionalCharacter
Indicates that the subject is a character that exists only in fiction rather than in real life.
-
C.
isFictionalPersonFrom
Indicates that a fictional person originates from or is associated with a particular place or source.
-
D.
hasFictionalType
chosen
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
E.
isFictionalBearer
Indicates that an entity serves as the (typically named) holder or possessor of something within a fictional or imaginary context.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1bbf5848190a698fdbec307886a |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.