Triple
T25948676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brad Wright |
E653911
|
entity |
| Predicate | hasWrittenForSeries |
P161248
|
FINISHED |
| Object | Stargate: The Ark of Truth |
—
|
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: Stargate: The Ark of Truth | Statement: [Brad Wright, hasWrittenForSeries, Stargate: The Ark of Truth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWrittenForSeries Context triple: [Brad Wright, hasWrittenForSeries, Stargate: The Ark of Truth]
-
A.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
B.
hasWrittenAbout
Indicates that one entity has authored content or material discussing, analyzing, or referencing another entity.
-
C.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
D.
hasPublicationSeries
Indicates that an entity is part of, or associated with, a particular publication series.
-
E.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 22, 2026, 8:43 a.m.