Triple
T31945464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sur les lagunes |
E815638
|
entity |
| Predicate | originalForces |
P203185
|
FINISHED |
| Object | voice and piano |
—
|
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: voice and piano | Statement: [Sur les lagunes, originalForces, voice and piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalForces Context triple: [Sur les lagunes, originalForces, voice and piano]
-
A.
primaryForces
Indicates a relationship where one or more forces are identified as the main or dominant contributors to an effect, behavior, or outcome among all forces involved.
-
B.
nativeForces
Indicates that certain forces or troops are indigenous to, or originate from, a particular place, group, or population.
-
C.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
D.
usesForcesFrom
Indicates that one entity applies or derives physical forces from another entity as part of its operation or behavior.
-
E.
primaryForce
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
- F. None of above. chosen
Provenance (4 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
| PDg | Predicate description generation | batch_6a0136e3d6ec8190898b5ab5a628a99d |
completed | May 11, 2026, 1:54 a.m. |
Created at: May 1, 2026, 12:06 a.m.