Triple
T1486682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Parcher |
E29479
|
entity |
| Predicate | alignmentFromProtagonistView |
P8789
|
FINISHED |
| Object | ally |
—
|
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: ally | Statement: [William Parcher, alignmentFromProtagonistView, ally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentFromProtagonistView Context triple: [William Parcher, alignmentFromProtagonistView, ally]
-
A.
perspectiveOf
chosen
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
B.
alignmentConcept
Indicates a conceptual or abstract relationship of alignment or correspondence between entities, such as agreement, compatibility, or shared orientation in some dimension.
-
C.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
D.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
E.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a3325881909bbc55efc04ad60f |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.