Triple
T34983063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paulatim Sed Firmiter |
E1008866
|
entity |
| Predicate | firmiterMeaning |
P182168
|
FINISHED |
| Object | firmly |
—
|
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: firmly | Statement: [Paulatim Sed Firmiter, firmiterMeaning, firmly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firmiterMeaning Context triple: [Paulatim Sed Firmiter, firmiterMeaning, firmly]
-
A.
deviceMeaning
Indicates that one entity specifies or conveys the functional meaning, purpose, or interpretation of a device-related entity.
-
B.
macMeaning
Indicates that one entity specifies or conveys the meaning or semantic interpretation of another entity within a mac-related context (e.g., a term, code, or identifier).
-
C.
tradeNameMeaning
Indicates that one entity is the meaning or semantic interpretation of another entity’s trade name.
-
D.
CISMeaning
Indicates that one concept, term, or symbol conveys, expresses, or stands for a particular meaning or interpretation in a given context.
-
E.
FitzElementMeaning
Indicates a relationship where an element is associated with, or conveys, a particular meaning or interpretive significance.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:01 p.m.