Triple
T37470925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emeni |
E931149
|
entity |
| Predicate | mechanicsSystem |
P162722
|
FINISHED |
| Object | Soulbinds |
—
|
NE NERFINISHED |
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: Soulbinds | Statement: [Emeni, mechanicsSystem, Soulbinds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicsSystem Context triple: [Emeni, mechanicsSystem, Soulbinds]
-
A.
mechanics
Indicates that an entity is involved in the study, design, or application of forces and motion (i.e., mechanical principles) in relation to another entity or system.
-
B.
mechanismComponent
chosen
Indicates that one entity functions as a component or part within the structure or operation of another entity conceived as a mechanism.
-
C.
mecanismo
Indicates a mechanism or means by which one entity brings about, enables, or explains the effect, function, or outcome in another entity.
-
D.
mechanicalFunction
Indicates that one entity serves as the mechanical role, operation, or function performed by another entity or system.
-
E.
mobilizationSystem
Indicates the system, method, or framework by which resources, people, or forces are organized and activated for coordinated action or deployment.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:17 p.m.