Triple
T34368305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Foundling |
E882080
|
entity |
| Predicate | refersToCharacterStatus |
P196226
|
FINISHED |
| Object | orphan |
—
|
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: orphan | Statement: [A Foundling, refersToCharacterStatus, orphan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToCharacterStatus Context triple: [A Foundling, refersToCharacterStatus, orphan]
-
A.
refersToCharacter
Indicates that one entity makes reference to, mentions, or points to a specific character as its subject.
-
B.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
C.
featuresCharacterWithStatus
Indicates that something (such as a work or scene) includes a character who has a specified status or condition.
-
D.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
E.
belongsToCharacter
Indicates that something is owned, associated with, or under the domain of a particular character.
- F. None of above. chosen
Provenance (4 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_69fe1639613c8190aaf1b4c8e2d861ba |
completed | May 8, 2026, 4:58 p.m. |
Created at: May 1, 2026, 1:58 a.m.