Triple
T114455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Royal Road |
E2313
|
entity |
| Predicate | usedUnder |
P2539
|
FINISHED |
| Object | royal authority |
—
|
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: royal authority | Statement: [The Royal Road, usedUnder, royal authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedUnder Context triple: [The Royal Road, usedUnder, royal authority]
-
A.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
B.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
implementedUnder
chosen
Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing entity.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564417848190a8a8a38e97348963 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.