Triple
T29338818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Covenants |
E743980
|
entity |
| Predicate | areRegisteredIn |
P53863
|
FINISHED |
| Object | United Nations Treaty Series |
—
|
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: United Nations Treaty Series | Statement: [International Covenants, areRegisteredIn, United Nations Treaty Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areRegisteredIn Context triple: [International Covenants, areRegisteredIn, United Nations Treaty Series]
-
A.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
B.
hasRegistrar
Indicates that an entity is formally recorded or overseen by a specific registrar organization or authority.
-
C.
mayBeRegisteredAs
Indicates that an entity has the possibility or eligibility to be formally registered under a particular status, category, or registry.
-
D.
officialRegisterOf
chosen
Indicates that one entity serves as the authoritative, formally maintained record or registry for another entity.
-
E.
hasRegistrationAuthority
Indicates that an entity is formally overseen, recorded, or certified by a specific authority responsible for its registration.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f669255db48190a9541c77cb9b5ede |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:32 p.m.