Triple
T1798526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN Board |
E39659
|
entity |
| Predicate | hasNumberOfLiaisons |
P32019
|
FINISHED |
| Object | 5 |
—
|
LITERAL FINISHED |
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: 5 | Statement: [ICANN Board, hasNumberOfLiaisons, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfLiaisons Context triple: [ICANN Board, hasNumberOfLiaisons, 5]
-
A.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
B.
hasTeleconnectionsWith
Indicates a relationship where changes or variations in one system, region, or variable are statistically linked to corresponding changes in another, often distant, system, region, or variable.
-
C.
hasNumberOfConcourses
Indicates the relationship specifying how many concourses are associated with a given entity.
-
D.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- F. None of above. chosen
Provenance (4 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab61b5c8988190bb2b46182a4eb5b4 |
completed | March 6, 2026, 11:22 p.m. |
Created at: March 4, 2026, 7:32 p.m.