Triple
T35993395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.E.H. |
E1040910
|
entity |
| Predicate | usedToPrecede |
P184488
|
FINISHED |
| Object | personal name of a 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: personal name of a prince | Statement: [H.E.H., usedToPrecede, personal name of a prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToPrecede Context triple: [H.E.H., usedToPrecede, personal name of a prince]
-
A.
precededByUse
Indicates that one use, action, or event occurs earlier in time and is directly followed by another specified use, action, or event.
-
B.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
C.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
D.
oftenPrecededBy
Indicates that one event, state, or item commonly occurs or appears before another in time or sequence.
-
E.
precededByInPosition
Indicates that one entity occurs or appears immediately before another entity in a specific ordered position or sequence.
- F. None of above. chosen
Provenance (4 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b35e32d481909ef0220e6f6ff4a8 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2c66054819083897e25edb65ba7 |
completed | May 3, 2026, 8:40 p.m. |
Created at: May 3, 2026, 4:07 p.m.