Triple
T20062820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Highness |
E499524
|
entity |
| Predicate | isWrittenBefore |
P103558
|
FINISHED |
| Object | given name of the royal person |
—
|
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: given name of the royal person | Statement: [Royal Highness, isWrittenBefore, given name of the royal person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWrittenBefore Context triple: [Royal Highness, isWrittenBefore, given name of the royal person]
-
A.
writtenBefore
chosen
Indicates that one written work was created or completed earlier in time than another written work.
-
B.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
C.
isWrittenAfterAmount
Indicates that one element is positioned in writing or notation after a specified quantity or amount.
-
D.
likelyWrittenFrom
Indicates that something (such as a text, statement, or perspective) is probably authored or expressed from the viewpoint, context, or position of a particular entity.
-
E.
laterWrittenDownAs
Indicates that something was recorded or documented in written form at a subsequent time after its original occurrence or expression.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66376f2d4819081b9e1b265650e5b |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.