Triple
T3992991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiko |
E87034
|
entity |
| Predicate | relationshipWithKingKong |
P38921
|
FINISHED |
| Object | son |
—
|
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: son | Statement: [Kiko, relationshipWithKingKong, son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithKingKong Context triple: [Kiko, relationshipWithKingKong, son]
-
A.
coKingWith
Indicates a relationship where two or more entities share kingship or jointly hold the position and authority of king at the same time.
-
B.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
C.
alsoKingOf
Indicates that an entity who is king of one place is simultaneously king of another place as well.
-
D.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
E.
superkingdom
Indicates the broadest taxonomic relationship in which one entity is classified as belonging to a particular superkingdom in the hierarchy of life.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.