Triple
T9226617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hale Tharp |
E221697
|
entity |
| Predicate | usedStructureFor |
P35482
|
FINISHED |
| Object | summer cabin |
—
|
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: summer cabin | Statement: [Hale Tharp, usedStructureFor, summer cabin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedStructureFor Context triple: [Hale Tharp, usedStructureFor, summer cabin]
-
A.
usedStructure
chosen
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
B.
usedInStructure
Indicates that something (such as a material, component, or element) is employed as part of the composition or construction of a larger structure.
-
C.
convertedStructureUse
Indicates that an entity’s original structural use has been changed to a different use or function.
-
D.
remainingStructuresUsedFor
Indicates that the remaining structures of an entity are utilized for a specified purpose or function.
-
E.
reusesStructureOf
Indicates that one entity adopts or incorporates the structural design or organization of another entity.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9ecef48190b8aa0e316d07cec7 |
completed | April 1, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.