Triple
T19920158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mt. Lebanon Historic District |
E478771
|
entity |
| Predicate | containsUse |
P137826
|
FINISHED |
| Object | residential |
—
|
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: residential | Statement: [Mt. Lebanon Historic District, containsUse, residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsUse Context triple: [Mt. Lebanon Historic District, containsUse, residential]
-
A.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
includeUses
Indicates that one entity incorporates or relies on another entity as a component, resource, or dependency in its use or operation.
-
C.
symbolicallyUses
Indicates that one entity employs another as a symbol or representation to convey meaning, ideas, or associations rather than for its literal or practical function.
-
D.
hasPresentUse
Indicates that an entity is currently being used or serving a particular function at the present time.
-
E.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c49d408190b3a42bada3675133 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.