Triple
T15929938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince royal |
E386296
|
entity |
| Predicate | canBeTranslatedAs |
P2303
|
FINISHED |
| Object | royal prince |
—
|
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 prince | Statement: [Prince royal, canBeTranslatedAs, royal prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeTranslatedAs Context triple: [Prince royal, canBeTranslatedAs, royal prince]
-
A.
canTranslateBetween
Indicates that an entity has the ability to translate or convert information accurately between two specified languages, formats, or representation systems.
-
B.
hasTranslation
chosen
Indicates that one entity is a translation or translated version of another entity in a different language.
-
C.
canTranslateAlong
Indicates that one entity is able to be moved or shifted along the path, direction, or frame of reference defined by another entity.
-
D.
hasTranslated
Indicates that one entity has rendered the content of another entity from one language into a different language.
-
E.
alsoTranslatedAs
Indicates that something has an alternative translation or rendering in another language or form.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.