Triple
T31515930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forestdale branch |
E804074
|
entity |
| Predicate | hasPhysicalPresence |
P178343
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Forestdale branch, hasPhysicalPresence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalPresence Context triple: [Forestdale branch, hasPhysicalPresence, yes]
-
A.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
B.
hasLocalPartyPresence
Indicates that a political party maintains an active organizational or operational presence within a specific local area or jurisdiction.
-
C.
traditionalPresenceIn
Indicates that an entity has a customary or historically established presence within a particular place, context, or setting.
-
D.
possiblePresenceIn
Indicates that an entity may be located in, occur in, or exist within a specified place, context, or container, without asserting that it is definitively present there.
-
E.
modernPresence
Indicates that something exists, appears, or is active in the contemporary or present-day context.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 30, 2026, 9:53 p.m.