Triple
T2636002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FACS |
E59746
|
entity |
| Predicate | indicatesStatus |
P8487
|
FINISHED |
| Object | fellow |
—
|
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: fellow | Statement: [FACS, indicatesStatus, fellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesStatus Context triple: [FACS, indicatesStatus, fellow]
-
A.
statusIndicates
chosen
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
B.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
C.
obtainedStatus
Indicates that an entity has received or achieved a particular status or condition as a result of some process or event.
-
D.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
E.
seeksStatusAs
Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8e1fffc81908e4921690098c8db |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.