Triple
T5420807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thing 1 |
E121242
|
entity |
| Predicate | duoMemberWith |
P46169
|
FINISHED |
| Object | Thing 2 |
—
|
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: Thing 2 | Statement: [Thing 1, duoMemberWith, Thing 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: duoMemberWith Context triple: [Thing 1, duoMemberWith, Thing 2]
-
A.
associatedWithDuo
chosen
Indicates a relationship in which an entity is linked or connected to a specific duo, typically implying involvement, collaboration, or relevance to that pair.
-
B.
triadMemberWith
Indicates a relationship where an entity is a member of a specific triad together with two other associated entities.
-
C.
someMembersMergedWith
Indicates that a subset of members from one group combined or integrated with members of another group to form a unified entity or subgroup.
-
D.
resonanceMembers
Indicates that multiple entities participate together in a shared resonance relationship or resonant state.
-
E.
sharesMembersWith
Indicates that two groups or collections have one or more members in common.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87eac41481908a4982db5d119edd |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.