Triple
T5342108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian passports |
E123966
|
entity |
| Predicate | documentColor |
P60
|
FINISHED |
| Object | burgundy red for ordinary passports |
—
|
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: burgundy red for ordinary passports | Statement: [Norwegian passports, documentColor, burgundy red for ordinary passports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentColor Context triple: [Norwegian passports, documentColor, burgundy red for ordinary passports]
-
A.
signatureColor
Indicates that an entity has a characteristic or defining color that is uniquely or primarily associated with it.
-
B.
colors
chosen
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
C.
documentSource
Indicates that one entity serves as the origin, provider, or provenance source for a given document.
-
D.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
E.
documentsCommunity
Indicates that an entity records, describes, or provides information about a particular community.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.