Triple
T10069964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadlock Field |
E213593
|
entity |
| Predicate | hasFamilyArea |
P91937
|
FINISHED |
| Object | family-friendly sections |
—
|
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: family-friendly sections | Statement: [Hadlock Field, hasFamilyArea, family-friendly sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyArea Context triple: [Hadlock Field, hasFamilyArea, family-friendly sections]
-
A.
hasFamilyHomeAt
Indicates that an entity has its family residence or primary household located at a specified place.
-
B.
hasIndoorArea
Indicates that an entity possesses or includes an area or space that is located indoors or within a building.
-
C.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
D.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
E.
hasHouseholdFeature
Indicates that a household possesses or includes a specific feature, attribute, or amenity.
- F. None of above. chosen
Provenance (4 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcffa045c8190a08db0bb74cb006a |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:58 p.m.