Triple
T21162609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gestalt |
E521477
|
entity |
| Predicate | combinationMethod |
P70673
|
FINISHED |
| Object | physical merging of component bodies |
—
|
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: physical merging of component bodies | Statement: [Gestalt, combinationMethod, physical merging of component bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinationMethod Context triple: [Gestalt, combinationMethod, physical merging of component bodies]
-
A.
combinationType
Indicates how multiple elements are combined or related to each other within a composite structure or operation.
-
B.
combinedIn
chosen
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
C.
comparisonMethod
Indicates the method or criteria used to compare two or more entities or values.
-
D.
laterCombination
Indicates that one entity is a combination or composite that occurs after, or is formed subsequent to, another entity or state.
-
E.
symbolCombines
Indicates that multiple symbols are merged or joined together to form a single composite symbol or representation.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72532e9348190ad37fe858843d0f5 |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.