Triple
T13150534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Fernando bus terminal |
E312450
|
entity |
| Predicate | typicallyOwnedBy |
P108790
|
FINISHED |
| Object | local government |
—
|
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: local government | Statement: [San Fernando bus terminal, typicallyOwnedBy, local government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyOwnedBy Context triple: [San Fernando bus terminal, typicallyOwnedBy, local government]
-
A.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
-
B.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
-
C.
ownedInPartBy
Indicates that an entity holds a partial (non‑full) ownership stake in another entity.
-
D.
targetOwnership
Indicates that one entity holds ownership or proprietary control over the target entity.
-
E.
ownedThrough
Indicates that one entity possesses or controls another indirectly via an intermediate entity, structure, or arrangement (such as a subsidiary, trust, or other vehicle).
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:11 p.m.