Triple
T3050525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US20030N1019 |
E83557
|
entity |
| Predicate | identifierScope |
P18655
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [US20030N1019, identifierScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifierScope Context triple: [US20030N1019, identifierScope, international]
-
A.
identificationScope
chosen
Indicates the contextual boundary or extent within which an entity is uniquely identified or recognized.
-
B.
scopeOfDeclaration
Indicates the syntactic region or context within which a particular declaration is valid and can be referenced.
-
C.
encodingScope
Indicates the range or extent of content or information that is covered, represented, or captured by a particular encoding.
-
D.
scopeDefinedBy
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained by another entity.
-
E.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bb1a46081908547a2f27cbf3446 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.