Triple
T38476257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malécites |
E915556
|
entity |
| Predicate | primaryStateInUSA |
P204673
|
FINISHED |
| Object | Maine |
E29256
|
NE 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: Maine | Statement: [Malécites, primaryStateInUSA, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStateInUSA Context triple: [Malécites, primaryStateInUSA, Maine]
-
A.
primaryStates
Indicates that certain states or conditions are the main or most fundamental ones within a given context or system.
-
B.
provinceState
Indicates that one entity is a province or state that is administratively contained within or associated with another, typically larger, territorial entity.
-
C.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
D.
stateName
Indicates that an entity is identified by or associated with a particular state’s name.
-
E.
traditionalStateOrTerritory
Indicates that an entity is located within, associated with, or belongs to a traditional state or territory as defined by historical or customary boundaries.
- F. None of above. chosen
Provenance (5 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ea7f45848190a62c3eede9933260 |
completed | June 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.