Triple
T9796641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Historic Landmarks in Texas |
E237732
|
entity |
| Predicate | includesTypeOfResource |
P3729
|
FINISHED |
| Object | building |
—
|
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: building | Statement: [National Historic Landmarks in Texas, includesTypeOfResource, building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTypeOfResource Context triple: [National Historic Landmarks in Texas, includesTypeOfResource, building]
-
A.
hasTypeOfResource
chosen
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
B.
isResourceFor
Indicates that one entity serves as a resource, support, or means of use for another entity.
-
C.
includesTypeOfObject
Indicates that one entity contains or encompasses another entity that is a specific type or category of object.
-
D.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
E.
includesTypeOfBody
Indicates that one entity encompasses or contains another entity classified as a specific type of body (e.g., physical, celestial, or organizational body).
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda34a53548190a8cb524381fe2bf9 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.