Triple
T30735955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N'Jobu |
E782553
|
entity |
| Predicate | coverIdentityLocation |
P170570
|
FINISHED |
| Object | Oakland, 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: Oakland, California | Statement: [N'Jobu, coverIdentityLocation, Oakland, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverIdentityLocation Context triple: [N'Jobu, coverIdentityLocation, Oakland, California]
-
A.
homeLocationInCoverIdentity
chosen
Indicates that an entity’s home location is specified within the context of its cover (false or assumed) identity.
-
B.
coverLocation
Indicates that one entity serves as a covering or protective layer positioned at or over a specific location of another entity.
-
C.
appearsInIdentity
Indicates that an entity is featured, referenced, or plays a role within a particular identity or identity-related context.
-
D.
coverIdentityCreatedBy
Indicates that a cover identity was created by a particular agent or entity.
-
E.
unveiledLocation
Indicates that an entity has revealed or made known the location of another entity or object.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 8:37 p.m.