Triple
T2154513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilbert, Arizona |
E47855
|
entity |
| Predicate | familyOrientation |
P8517
|
FINISHED |
| Object | family-oriented community |
—
|
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-oriented community | Statement: [Gilbert, Arizona, familyOrientation, family-oriented community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyOrientation Context triple: [Gilbert, Arizona, familyOrientation, family-oriented community]
-
A.
familyAspect
chosen
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
B.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
-
D.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
E.
parentFormation
Indicates that one geological formation serves as the larger or originating unit from which another formation is derived or classified.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe64fdf081909a5ea6818bddd18c |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.