Triple
T27343354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise (OV-101) |
E684167
|
entity |
| Predicate | unveilingLocation |
P47308
|
FINISHED |
| Object | Palmdale, California |
—
|
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: Palmdale, California | Statement: [Enterprise (OV-101), unveilingLocation, Palmdale, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unveilingLocation Context triple: [Enterprise (OV-101), unveilingLocation, Palmdale, California]
-
A.
unveiledLocation
Indicates that an entity has revealed or made known the location of another entity or object.
-
B.
plotLocation
Indicates the relationship between a creative work and the place or setting where its story or events occur.
-
C.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
D.
subjectLocation
chosen
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
E.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62b9f5514819088c3a1e11c65a9af |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:44 a.m.