Triple
T26823433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of San Fernando |
E675313
|
entity |
| Predicate | hasDistinctCivicIdentityFrom |
P27113
|
FINISHED |
| Object | City of Los Angeles |
—
|
NE NERFINISHED |
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: City of Los Angeles | Statement: [City of San Fernando, hasDistinctCivicIdentityFrom, City of Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctCivicIdentityFrom Context triple: [City of San Fernando, hasDistinctCivicIdentityFrom, City of Los Angeles]
-
A.
hasCivicIdentity
Indicates that an entity possesses a recognized status, role, or affiliation within a civic, social, or political community.
-
B.
hasCivicNumber
Indicates that an entity is associated with a specific civic (street) number used for its address.
-
C.
hasDistinctIdentity
chosen
Indicates that an entity possesses its own unique, distinguishable identity separate from other entities.
-
D.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
E.
hasCivilianIdentity
Indicates that an entity possesses a non-superhero, everyday personal identity used in civilian life.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 4:57 a.m.