Triple
T26913304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Nichols |
E677448
|
entity |
| Predicate | fieldAssociation |
P6979
|
FINISHED |
| Object | architecture |
—
|
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: architecture | Statement: [William Nichols, fieldAssociation, architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldAssociation Context triple: [William Nichols, fieldAssociation, architecture]
-
A.
relatedField
chosen
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
B.
antAssociation
Indicates a relationship in which one entity is associated or interacts in a specific, notable way with ants.
-
C.
endedAssociationWith
Indicates that a previously existing association or relationship between two entities has been terminated or discontinued.
-
D.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
E.
elementalAssociation
Indicates an association where one entity is linked or related to a particular element or elemental property (such as fire, water, earth, or air).
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 6:03 a.m.