Triple
T34910691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the House of Grimaldi |
E1006854
|
entity |
| Predicate | earliestUseRegion |
P14489
|
FINISHED |
| Object | Genoa |
—
|
NE NERFINISHED |
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: Genoa | Statement: [Arms of the House of Grimaldi, earliestUseRegion, Genoa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestUseRegion Context triple: [Arms of the House of Grimaldi, earliestUseRegion, Genoa]
-
A.
locationOfEarlyUse
chosen
Indicates the place where something was first or among the earliest instances to be used or applied.
-
B.
historicalPeriodOfFirstUse
Indicates the historical time period during which something was first used or came into use.
-
C.
earliestUnificationCenter
Indicates the location that served as the first or primary center where separate entities were brought together into a unified whole.
-
D.
regionOfEarlyExpansion
Indicates that a location served as an initial area where an entity, influence, or phenomenon began to grow or spread outward.
-
E.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4 p.m.