Triple
T32503323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moclan society |
E830719
|
entity |
| Predicate | notableCharacterRepresentative |
P89514
|
FINISHED |
| Object | Bortus |
E34009
|
NE 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: Bortus | Statement: [Moclan society, notableCharacterRepresentative, Bortus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterRepresentative Context triple: [Moclan society, notableCharacterRepresentative, Bortus]
-
A.
notableConstituent
Indicates that one entity is a significant or prominent component, part, or member of another entity.
-
B.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
C.
notableLivingRepresentative
chosen
Indicates that one entity is a prominent currently-living example or representative of another entity (such as a group, category, or organization).
-
D.
notablePartyRepresentation
Indicates that an entity is significantly or prominently represented or involved as a party in a particular event, case, or context.
-
E.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
- F. None of above.
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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34705a55008190b5cf60cab8aa145b |
completed | June 18, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:59 a.m.