Triple
T20103016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wood Way |
E496593
|
entity |
| Predicate | reflectsInterestIn |
P72119
|
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: [The Wood Way, reflectsInterestIn, architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsInterestIn Context triple: [The Wood Way, reflectsInterestIn, architecture]
-
A.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
B.
reflectsInterestOfAuthorIn
chosen
Indicates that something expresses or reveals the author’s interest in a particular subject, entity, or topic.
-
C.
representsInterestOf
Indicates that one entity expresses, holds, or embodies an interest, concern, or stake in another entity or subject.
-
D.
recognizedInterest
Indicates that one entity has formally acknowledged or identified another entity’s interest in something as valid or relevant.
-
E.
publicInterestStatus
Indicates that something has been evaluated or designated in terms of its relevance, importance, or impact to the general public or society at large.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6667170a4819085d07a4188ded541 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:27 p.m.