Triple
T20454370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hideaway, Texas |
E501735
|
entity |
| Predicate | isRetirementOriented |
P54003
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hideaway, Texas, isRetirementOriented, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRetirementOriented Context triple: [Hideaway, Texas, isRetirementOriented, true]
-
A.
appliesToRetirementStatus
Indicates that the subject is relevant or applicable specifically to an entity’s retirement status or condition.
-
B.
plannedRetirement
Indicates that an entity has scheduled or intends to end its active role or service at a specified future time.
-
C.
retirementPeriod
Indicates the time span during which an entity is considered to be retired or in retirement status.
-
D.
associatedWithRetirement
chosen
Indicates a relationship in which something is connected to, involved in, or relevant to the state, process, or context of retirement.
-
E.
retirementPattern
Indicates the typical way or schedule in which an entity withdraws from active service, work, 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68d04ca4081909b428c31d16fca10 |
completed | April 20, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.