Triple
T7396777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paolone |
E170640
|
entity |
| Predicate | suffixFunction |
P23285
|
FINISHED |
| Object | Italian augmentative 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: Italian augmentative suffix | Statement: [Paolone, suffixFunction, Italian augmentative suffix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suffixFunction Context triple: [Paolone, suffixFunction, Italian augmentative suffix]
-
A.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
B.
keyFunction
Indicates that an entity serves as a primary or essential mechanism enabling a particular operation, role, or outcome for another entity.
-
C.
successorFunction
Indicates the relationship where one entity is defined as the immediate next or following element in a sequence or ordered set relative to another.
-
D.
associatedFunction
chosen
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
E.
namingFunction
Indicates a relationship where one entity serves as the name or naming mechanism assigned to 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f248f79c819094b1d1e2c3d511d1 |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.