Triple
T34197492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nulli Secundus |
E877281
|
entity |
| Predicate | secundusExtendedMeaning |
P141387
|
FINISHED |
| Object | second |
—
|
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: second | Statement: [Nulli Secundus, secundusExtendedMeaning, second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secundusExtendedMeaning Context triple: [Nulli Secundus, secundusExtendedMeaning, second]
-
A.
secundusBasicMeaning
Indicates that something holds a secondary, subordinate, or lesser primary meaning in relation to another meaning or interpretation.
-
B.
secondPartMeaning
Indicates that something represents the latter or subsequent portion of a larger whole in terms of its meaning or semantic content.
-
C.
secondDefinition
Indicates that one entity serves as an alternative or secondary definition or meaning for another entity.
-
D.
secondWord
Indicates that one entity is the second word in sequence immediately following the first entity in a text or utterance.
-
E.
hasMeaningExtension
chosen
Indicates that one entity represents an extended, elaborated, or more detailed meaning of another entity’s meaning.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:55 a.m.