Triple
T1859864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.O.L.H. |
E41789
|
entity |
| Predicate | usedInBiographicalNotices |
P6570
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [G.O.L.H., usedInBiographicalNotices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInBiographicalNotices Context triple: [G.O.L.H., usedInBiographicalNotices, yes]
-
A.
hasPartInBiography
Indicates that a person or entity is featured or plays a role within someone’s biographical account.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
includesBiographiesOf
chosen
Indicates that one entity contains or features biographical information about another entity.
-
D.
usedInMediaOf
Indicates that something (e.g., a work, element, or content) is employed or appears within a particular media work or production.
-
E.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.