Triple
T2862910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nutmegger |
E63366
|
entity |
| Predicate | hasParticularFormOf |
P37104
|
FINISHED |
| Object | gentilic |
—
|
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: gentilic | Statement: [Nutmegger, hasParticularFormOf, gentilic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticularFormOf Context triple: [Nutmegger, hasParticularFormOf, gentilic]
-
A.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
B.
isGivenNameFormOf
Indicates that one name is a given-name variant or form derived from another name.
-
C.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
D.
compositionalForm
Indicates the structural or formal composition that defines how parts are organized or combined within something.
-
E.
hasSurfaceForm
chosen
Indicates that an abstract concept, entity, or linguistic unit is realized or expressed in a specific textual or lexical form.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfb6e6988190b832ee05d8420633 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.