Triple
T36825983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N-1 |
E910011
|
entity |
| Predicate | registrationDesignationOf |
P176960
|
FINISHED |
| Object | Norge |
—
|
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: Norge | Statement: [N-1, registrationDesignationOf, Norge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationDesignationOf Context triple: [N-1, registrationDesignationOf, Norge]
-
A.
registrationOf
chosen
Indicates that one entity is the formal record or enrollment of another entity in an official system, registry, or process.
-
B.
mountDesignation
Indicates that one entity is designated or assigned as the mount (e.g., riding or support animal/vehicle) for another entity.
-
C.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
D.
bdDesignation
Indicates that one entity is formally assigned or designated as having a particular role, status, or classification in relation to another entity.
-
E.
designationAct
Indicates an official act by which an authority formally assigns, names, or appoints an entity to a specific role, status, or function.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca9c9ef88190b71bcc6f5b4a6182 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.