Triple
T35971462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tours de Broel |
E1040294
|
entity |
| Predicate | isPairWith |
P46528
|
FINISHED |
| Object | each other |
—
|
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: each other | Statement: [Tours de Broel, isPairWith, each other]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPairWith Context triple: [Tours de Broel, isPairWith, each other]
-
A.
isPairOf
chosen
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
-
B.
isTwinWith
Indicates that two entities are twins, sharing the same birth parents and being born at (or very near) the same time.
-
C.
isPerfectPairing
Indicates that two entities complement each other exceptionally well, forming an ideal or highly compatible combination.
-
D.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.