Triple
T27860073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meadow Lane (street) |
E704200
|
entity |
| Predicate | isTypicallyCharacterizedBy |
P662
|
FINISHED |
| Object | nearby green spaces |
—
|
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: nearby green spaces | Statement: [Meadow Lane (street), isTypicallyCharacterizedBy, nearby green spaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyCharacterizedBy Context triple: [Meadow Lane (street), isTypicallyCharacterizedBy, nearby green spaces]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
commonlyIdentifiedWith
Indicates that two entities are widely regarded or treated as the same or equivalent, even if they are formally distinct.
-
C.
hasTypicalConditions
Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
-
D.
oftenPresentedAs
Indicates that one entity is frequently depicted, portrayed, or shown in the form or role of another entity.
-
E.
manifestationsInclude
Indicates that one entity’s manifestations or concrete expressions contain or encompass those of another entity.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 6:17 p.m.