Triple
T23534289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andare insieme, andare lontano |
E576651
|
entity |
| Predicate | hasMottoLikeTheme |
P153149
|
FINISHED |
| Object | collective progress over individualism |
—
|
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: collective progress over individualism | Statement: [Andare insieme, andare lontano, hasMottoLikeTheme, collective progress over individualism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoLikeTheme Context triple: [Andare insieme, andare lontano, hasMottoLikeTheme, collective progress over individualism]
-
A.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
B.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
C.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
D.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
E.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae14ae3c8190aa2714ea07a4658a |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:10 p.m.