Triple
T14110319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcory |
E339617
|
entity |
| Predicate | hasResidentialNeighborhood |
P4813
|
FINISHED |
| Object | Zone 4 |
—
|
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: Zone 4 | Statement: [Marcory, hasResidentialNeighborhood, Zone 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentialNeighborhood Context triple: [Marcory, hasResidentialNeighborhood, Zone 4]
-
A.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
B.
hasNeighbourhood
chosen
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
C.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
D.
isResidentialTown
Indicates that a town is primarily used or designated for residential living rather than for commercial, industrial, or other primary purposes.
-
E.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600e6a688190a1243a30ae9b7157 |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.