Triple
T2295865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodlawn, Maryland |
E51610
|
entity |
| Predicate | hasFeatureClass |
P39038
|
FINISHED |
| Object | populated place |
—
|
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: populated place | Statement: [Woodlawn, Maryland, hasFeatureClass, populated place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeatureClass Context triple: [Woodlawn, Maryland, hasFeatureClass, populated place]
-
A.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
-
C.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
D.
hasServiceClass
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
-
E.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcd0d01ac8190935fe904905cb233 |
completed | March 7, 2026, 7 a.m. |
Created at: March 4, 2026, 7:49 p.m.