Triple
T33751044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | corridinho |
E864841
|
entity |
| Predicate | pairInteraction |
P133310
|
FINISHED |
| Object | hand-holding |
—
|
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: hand-holding | Statement: [corridinho, pairInteraction, hand-holding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairInteraction Context triple: [corridinho, pairInteraction, hand-holding]
-
A.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
B.
interactionBetween
chosen
Indicates a reciprocal or mutual action, influence, or communication occurring between two or more entities.
-
C.
plateInteraction
Indicates an interaction involving a plate, such as using, handling, or otherwise engaging with it in a specific context.
-
D.
bindingInteraction
Indicates a specific binding relationship where one entity physically or functionally attaches to, or forms a stable association with, another entity.
-
E.
pairedSingleWith
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb8ffae48190a4244047eab033e4 |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96ea0c08190902a3d0e1f263e8c |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:45 a.m.