Triple
T18508835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diana Vaughan |
E452274
|
entity |
| Predicate | truthStatus |
P29186
|
FINISHED |
| Object | entirely fictitious biography |
—
|
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: entirely fictitious biography | Statement: [Diana Vaughan, truthStatus, entirely fictitious biography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: truthStatus Context triple: [Diana Vaughan, truthStatus, entirely fictitious biography]
-
A.
trustedStatus
Indicates that one entity regards another as reliable, dependable, or worthy of confidence in a given context.
-
B.
realityStatus
chosen
Indicates the relationship between an entity and its state of existence or authenticity within a given context or world (e.g., real, fictional, hypothetical, simulated).
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
E.
positionOnTruth
Indicates the stance or viewpoint an entity holds regarding the truth or falsity of a given claim or proposition.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53344c6b081908e780ed5c815a766 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.