Triple
T34011515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan Mountstuart |
E872123
|
entity |
| Predicate | hasFictionalRelationshipsWith |
P34570
|
FINISHED |
| Object | Lottie |
—
|
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: Lottie | Statement: [Logan Mountstuart, hasFictionalRelationshipsWith, Lottie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalRelationshipsWith Context triple: [Logan Mountstuart, hasFictionalRelationshipsWith, Lottie]
-
A.
fictionalRelationship
chosen
Indicates a relationship that exists only within a fictional or imagined context between entities.
-
B.
hasFictionalSibling
Indicates that one entity is a fictional character who is a sibling of another entity.
-
C.
hasFictionalFamilyMember
Indicates that one entity has another entity as a family member within a fictional or imagined context.
-
D.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
E.
hasFictionalRomanticInterest
Indicates that one entity is portrayed as having a romantic attraction or interest toward another entity within a fictional 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: May 1, 2026, 1:51 a.m.