Triple
T14936795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Máni |
E372415
|
entity |
| Predicate | capturedCompanion |
P47579
|
FINISHED |
| Object | children Bil and Hjuki |
—
|
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: children Bil and Hjuki | Statement: [Máni, capturedCompanion, children Bil and Hjuki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedCompanion Context triple: [Máni, capturedCompanion, children Bil and Hjuki]
-
A.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
C.
successorCompanion
Indicates that one entity serves as the subsequent or replacement companion to another entity in a sequence or timeline.
-
D.
capturedOff
chosen
Indicates that one entity has taken another entity away or into custody, removing it from its original location or control.
-
E.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64904d88190b6b4140da8e8199d |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:37 a.m.