Triple
T8830689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Explorare, Inventire, Disciplinare |
E210130
|
entity |
| Predicate | translationHint |
P84892
|
FINISHED |
| Object | To explore |
—
|
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: To explore | Statement: [Explorare, Inventire, Disciplinare, translationHint, To explore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translationHint Context triple: [Explorare, Inventire, Disciplinare, translationHint, To explore]
-
A.
translationDirection
Indicates the source and target languages involved in a translation, specifying the direction from the original language to the translated language.
-
B.
translationProperty
Indicates a relationship where one entity serves as a translated counterpart or translation-specific attribute of another entity.
-
C.
translationOn
Indicates that one entity is a translation of another entity, typically expressing the same content in a different language or linguistic form.
-
D.
translationMethod
Indicates the technique or process used to translate content from one language or form to another.
-
E.
translationSource
Indicates that one entity serves as the original text or content from which another entity is translated.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc604db0788190a3082467d80fdaf5 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:47 p.m.