Triple
T29050371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother Box |
E735248
|
entity |
| Predicate | bondingMechanism |
P20814
|
FINISHED |
| Object | forms symbiotic relationship with owner |
—
|
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: forms symbiotic relationship with owner | Statement: [Mother Box, bondingMechanism, forms symbiotic relationship with owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bondingMechanism Context triple: [Mother Box, bondingMechanism, forms symbiotic relationship with owner]
-
A.
typicalBonding
Indicates a usual or characteristic bonding relationship that commonly occurs between the involved entities.
-
B.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
C.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
D.
bondsFormed
Indicates that a connection or attachment has been created between two or more entities.
-
E.
formationMechanism
chosen
Indicates the process or mechanism by which something is formed, created, or brought into existence.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6606492ac81909f591f2ac7469b13 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:08 a.m.