Triple
T24896672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gogra |
E623162
|
entity |
| Predicate | identityPrimarilyTiedTo |
P68775
|
FINISHED |
| Object | Kauriala |
—
|
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: Kauriala | Statement: [Gogra, identityPrimarilyTiedTo, Kauriala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identityPrimarilyTiedTo Context triple: [Gogra, identityPrimarilyTiedTo, Kauriala]
-
A.
identityStoredIn
Indicates that an entity’s identity information is kept or recorded within another entity or storage medium.
-
B.
identityDerivedFrom
Indicates that one entity’s identity is obtained, inferred, or constructed based on another entity’s identity.
-
C.
realmAssociatedWith
chosen
Indicates an association or connection between an entity and a particular realm, domain, or sphere with which it is linked or to which it pertains.
-
D.
identityStatus
Indicates the current state or condition of an entity’s identity, such as whether it is verified, active, pending, or otherwise classified.
-
E.
relatedIdentity
Indicates that two identities are connected or associated with each other in some meaningful way, such as being alternate, linked, or otherwise contextually related.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:26 a.m.