Triple
T6909859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of José Martí |
E159902
|
entity |
| Predicate | hasMottoOrInspiration |
P47757
|
FINISHED |
| Object | ideas and legacy of José Martí |
—
|
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: ideas and legacy of José Martí | Statement: [Order of José Martí, hasMottoOrInspiration, ideas and legacy of José Martí]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrInspiration Context triple: [Order of José Martí, hasMottoOrInspiration, ideas and legacy of José Martí]
-
A.
hasMottoOrigin
chosen
Indicates that a motto originates from, or is derived from, a particular source, place, or context.
-
B.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
C.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
D.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
E.
hasMottoContext
Indicates that an entity’s motto is associated with or applies within a specific contextual setting or scope.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9c00e948190b103a2b2a2738bb1 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.