Triple
T34983062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paulatim Sed Firmiter |
E1008866
|
entity |
| Predicate | paulatimMeaning |
P67029
|
FINISHED |
| Object | little by little |
—
|
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: little by little | Statement: [Paulatim Sed Firmiter, paulatimMeaning, little by little]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paulatimMeaning Context triple: [Paulatim Sed Firmiter, paulatimMeaning, little by little]
-
A.
PSEMeaning
Indicates that one entity expresses, conveys, or encodes a particular meaning or semantic content in relation to another.
-
B.
meaningViaPatricia
Indicates that something’s meaning, interpretation, or understanding is conveyed, mediated, or determined through an intermediary named Patricia.
-
C.
PBMeaning
chosen
Indicates that something conveys, expresses, or represents a particular sense, idea, or significance.
-
D.
hasMeaningViaJohn
Indicates that something possesses or conveys its meaning specifically through John as the interpretive or mediating agent.
-
E.
PoloMeaning
Indicates that one entity represents the meaning, definition, or semantic interpretation of the term or concept "Polo" for another entity.
- 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_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. |
Created at: May 3, 2026, 4:01 p.m.