Triple
T2120955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Governor's Mansion |
E43919
|
entity |
| Predicate | isOpenFor |
P2556
|
FINISHED |
| Object | public tours (with security restrictions) |
—
|
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: public tours (with security restrictions) | Statement: [Texas Governor's Mansion, isOpenFor, public tours (with security restrictions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOpenFor Context triple: [Texas Governor's Mansion, isOpenFor, public tours (with security restrictions)]
-
A.
isOpenTo
chosen
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
B.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
-
C.
openedForCurrentUse
Indicates that an entity has been opened and is currently available for its intended use or operation.
-
D.
openStatus
Indicates whether an entity (such as a place, service, or resource) is currently open or available for use.
-
E.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb3404348190bc843022fbd2b4d0 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.