Triple
T32519268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN Non-Contracted Parties House |
E831138
|
entity |
| Predicate | counterpartHouse |
P6587
|
FINISHED |
| Object | ICANN Contracted Parties House |
—
|
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: ICANN Contracted Parties House | Statement: [ICANN Non-Contracted Parties House, counterpartHouse, ICANN Contracted Parties House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counterpartHouse Context triple: [ICANN Non-Contracted Parties House, counterpartHouse, ICANN Contracted Parties House]
-
A.
counterpartService
Indicates that one service functions as the corresponding or matching service to another within a defined relationship or context.
-
B.
hasCounterpart
chosen
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
C.
counterpartTerm
Indicates that one term serves as a corresponding or equivalent term to another within a specific relational or comparative context.
-
D.
counterpartRelation
Indicates a reciprocal relationship where two entities serve as corresponding or equivalent counterparts to each other in a given context.
-
E.
counterpartLocatedAt
Indicates that one entity serves as the corresponding or matching counterpart of another entity at a specific location or site.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: May 1, 2026, 1 a.m.