Triple
T17169223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | By Sea, By Land |
E416684
|
entity |
| Predicate | hasOriginalLanguageMotto |
P8987
|
FINISHED |
| Object | Per Mare, Per Terram |
—
|
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: Per Mare, Per Terram | Statement: [By Sea, By Land, hasOriginalLanguageMotto, Per Mare, Per Terram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalLanguageMotto Context triple: [By Sea, By Land, hasOriginalLanguageMotto, Per Mare, Per Terram]
-
A.
hasMottoOrigin
Indicates that a motto originates from, or is derived from, a particular source, place, or context.
-
B.
mottoOriginal
chosen
Indicates that one entity is the original wording or form of another entity’s motto.
-
C.
languageOfMotto
Indicates the language in which a motto is written or expressed.
-
D.
hasMottoLanguageContext
Indicates that a motto is associated with a specific language context in which it is expressed or interpreted.
-
E.
earlierMottoLanguage
Indicates that the language was used in an earlier version or period of the entity’s motto compared to another language or later motto form.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f9173ee48190bc46622c78479603 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.