Triple
T27860076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meadow Lane (street) |
E704200
|
entity |
| Predicate | hasCommonLandUseAlong |
P199673
|
FINISHED |
| Object | housing |
—
|
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: housing | Statement: [Meadow Lane (street), hasCommonLandUseAlong, housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonLandUseAlong Context triple: [Meadow Lane (street), hasCommonLandUseAlong, housing]
-
A.
hasCommonArea
Indicates that two or more entities share a mutual physical or conceptual space used or accessible by all of them.
-
B.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
C.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
D.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
E.
haveSharedInfrastructure
Indicates that two or more entities use or depend on the same underlying physical or virtual infrastructure resources.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
| PDg | Predicate description generation | batch_69ff4fc5289c819084abd5ede185e96b |
completed | May 9, 2026, 3:16 p.m. |
Created at: April 27, 2026, 6:17 p.m.