Triple
T36920624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Lady Ludlow |
E913186
|
entity |
| Predicate | hasAristocraticProtagonist |
P174345
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [My Lady Ludlow, hasAristocraticProtagonist, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAristocraticProtagonist Context triple: [My Lady Ludlow, hasAristocraticProtagonist, true]
-
A.
hasAristocraticHero
chosen
Indicates that the subject work or narrative features a main hero who belongs to the aristocracy or noble class.
-
B.
hasAristocraticNarrator
Indicates that the work’s narrator is a member of the aristocracy or noble class.
-
C.
aristocraticRole
Indicates that an entity holds or is associated with a formal position, title, or function within an aristocratic or noble hierarchy.
-
D.
hasRelativeInAristocracy
Indicates that an entity has at least one relative who belongs to the aristocracy or noble class.
-
E.
isFictionalAristocratIn
Indicates that a character is a fictional member of the aristocracy who appears in or belongs to a specified work, setting, or universe.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: May 3, 2026, 4:13 p.m.