Triple
T15139779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal designation (Koninklijk) |
E361652
|
entity |
| Predicate | usedAsPrefix |
P93740
|
FINISHED |
| Object | company name |
—
|
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: company name | Statement: [Royal designation (Koninklijk), usedAsPrefix, company name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsPrefix Context triple: [Royal designation (Koninklijk), usedAsPrefix, company name]
-
A.
usedAsPrefixIn
chosen
Indicates that one element functions as a leading prefix component in the formation or representation of another element.
-
B.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
usedAsSuffixTo
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
D.
usedAsNameSourceFor
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
-
E.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c46a248190a2364092d40274f3 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.