Triple
T25703403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belinda |
E644522
|
entity |
| Predicate | hasSocialStatusInFiction |
P77957
|
FINISHED |
| Object | upper-class woman |
—
|
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: upper-class woman | Statement: [Belinda, hasSocialStatusInFiction, upper-class woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialStatusInFiction Context triple: [Belinda, hasSocialStatusInFiction, upper-class woman]
-
A.
hasReputationInFiction
Indicates that an entity is known or regarded in a particular way within fictional works or narratives.
-
B.
hasRankInFiction
Indicates that a fictional character or entity holds a specific rank, title, or hierarchical position within a fictional context or universe.
-
C.
fictionalStatus
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
-
D.
fictionalSocialClass
chosen
Indicates a relationship where an entity is assigned to or associated with a social class that exists only within a fictional or imagined context.
-
E.
hasRelativeInFiction
Indicates that one entity has a relative or family member who appears as a character within a fictional work associated with the other 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 8:59 p.m.