Triple
T64311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L'union fait la force |
E1278
|
entity |
| Predicate | translation |
P2303
|
FINISHED |
| Object | Unity makes strength |
—
|
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: Unity makes strength | Statement: [L'union fait la force, translation, Unity makes strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translation Context triple: [L'union fait la force, translation, Unity makes strength]
-
A.
hasTranslation
chosen
Indicates that one entity is a translation or translated version of another entity in a different language.
-
B.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
C.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
-
D.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
E.
restriction
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.