Triple
T2014097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Pioneer Corps |
E43754
|
entity |
| Predicate | receivedRoyalPrefix |
P8257
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [Royal Pioneer Corps, receivedRoyalPrefix, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedRoyalPrefix Context triple: [Royal Pioneer Corps, receivedRoyalPrefix, 1946]
-
A.
monarchGrantingRoyalPrefix
chosen
Indicates that a monarch has officially authorized the use of a royal prefix (such as "Royal") for a person, organization, title, or entity.
-
B.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
C.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
D.
previousHonorificPrefix
Indicates that one entity was formerly used as an honorific prefix or title for another entity before being changed or replaced.
-
E.
receivedTitle
Indicates that an entity has been formally granted or awarded a specific title or honor.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b42d508190bf2b63132bb2ad77 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.