Triple
T6525877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana state historic site |
E151299
|
entity |
| Predicate | appliesToTypeOfPlace |
P16688
|
FINISHED |
| Object | buildings |
—
|
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: buildings | Statement: [Indiana state historic site, appliesToTypeOfPlace, buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToTypeOfPlace Context triple: [Indiana state historic site, appliesToTypeOfPlace, buildings]
-
A.
placeType
chosen
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
B.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
C.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
appliesToTransportFacilityType
Indicates that something is relevant or applicable specifically to a particular type or category of transport facility.
-
E.
appliesToTerritorialEntity
Indicates that something (such as a rule, measure, status, or attribute) is valid for, relevant to, or in effect within a specific territorial 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ada77b448190b6e0e07494fb4dd3 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.