Triple
T150690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clementine |
E3423
|
entity |
| Predicate | hasNameElement |
P3097
|
FINISHED |
| Object | -ine suffix |
—
|
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: -ine suffix | Statement: [Clementine, hasNameElement, -ine suffix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameElement Context triple: [Clementine, hasNameElement, -ine suffix]
-
A.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
B.
usesElement
chosen
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
C.
hasLatinName
Indicates that an entity is associated with a specific Latin (scientific) name.
-
D.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
E.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580dda148190a522e0ac276d5f33 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.