Triple
T13344761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conchobhar |
E317919
|
entity |
| Predicate | famousBearerRole |
P65465
|
FINISHED |
| Object | legendary king of Ulster |
—
|
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: legendary king of Ulster | Statement: [Conchobhar, famousBearerRole, legendary king of Ulster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousBearerRole Context triple: [Conchobhar, famousBearerRole, legendary king of Ulster]
-
A.
notableBearerFullName
Indicates that a full personal name is that of a notable or well-known bearer associated with the referenced entity.
-
B.
notableBearerDescription
chosen
Indicates that the subject has a notable bearer, with the object providing a textual description of that bearer’s significance or identity.
-
C.
mostFamousBearer
Indicates that one entity is the most widely recognized or renowned individual associated with a particular name, title, or attribute compared to all other bearers of it.
-
D.
bearerByname
Indicates that an entity is known or referred to by a particular byname or secondary name.
-
E.
associatedWithRoleOfNameBearer
Indicates that an entity is connected to or involved with the specific role or function held by a designated name bearer.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8839b48190b164414b418e756c |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.