Triple
T4690422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Country Teams |
E104020
|
entity |
| Predicate | compositionVariesBy |
P58820
|
FINISHED |
| Object | country context |
—
|
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: country context | Statement: [UN Country Teams, compositionVariesBy, country context]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionVariesBy Context triple: [UN Country Teams, compositionVariesBy, country context]
-
A.
structureVariesBy
Indicates that the structure or configuration of one entity changes depending on or is different for another specified factor or context.
-
B.
termVariesBy
Indicates that the value or meaning of a term changes depending on a specified factor, such as context, dimension, or condition.
-
C.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
D.
varietyOf
Indicates that one entity is a specific type, kind, or variant of another, more general entity.
-
E.
lengthVariesBy
Indicates that the length of one entity changes or differs depending on another specified factor or condition.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd660414b08190ab37467755d383b5 |
completed | March 20, 2026, 3:21 p.m. |
Created at: March 20, 2026, 1:16 p.m.