Triple
T13527315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | complementarity principle |
E323045
|
entity |
| Predicate | involvesPropertyPair |
P46528
|
FINISHED |
| Object | wave-like behavior |
—
|
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: wave-like behavior | Statement: [complementarity principle, involvesPropertyPair, wave-like behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesPropertyPair Context triple: [complementarity principle, involvesPropertyPair, wave-like behavior]
-
A.
parityProperty
Indicates that a relationship or quantity has a specific parity (such as being even, odd, or matching in parity) according to the defined property.
-
B.
isPairOf
chosen
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
-
C.
identifiesPropertyOf
Indicates that one entity specifies or denotes a particular property or attribute belonging to another entity.
-
D.
isContributingPropertyTo
Indicates that one property plays a role in producing, influencing, or determining another property or overall outcome.
-
E.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafb8e0cc8190b47f6aeb8ced470e |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.