Triple
T29571645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griffith Company |
E753326
|
entity |
| Predicate | notableLocationOfProjects |
P115582
|
FINISHED |
| Object | Los Angeles, California |
E158960
|
NE 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: Los Angeles, California | Statement: [Griffith Company, notableLocationOfProjects, Los Angeles, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLocationOfProjects Context triple: [Griffith Company, notableLocationOfProjects, Los Angeles, California]
-
A.
notableRegionOfProjects
chosen
Indicates that a region is particularly significant or prominent as the location or focus of certain projects.
-
B.
notableProjectFor
Indicates that a particular project is especially significant, prominent, or noteworthy for a given entity.
-
C.
locationOfMajorProject
Indicates the place where a significant or primary project is based, conducted, or implemented.
-
D.
notableProjectArea
Indicates that an entity has a significant or distinguished project specifically associated with a particular area or domain.
-
E.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
- F. None of above.
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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a267e9db4b88190983edd211df4da9c |
completed | June 8, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 5:59 p.m.