Triple
T10568706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matinicus Isle, Maine |
E249420
|
entity |
| Predicate | hasStateFIPSCode |
P227
|
FINISHED |
| Object | 23 |
—
|
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: 23 | Statement: [Matinicus Isle, Maine, hasStateFIPSCode, 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateFIPSCode Context triple: [Matinicus Isle, Maine, hasStateFIPSCode, 23]
-
A.
FIPSCode
chosen
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
B.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
C.
federalStateCode
Indicates that an entity is associated with, governed by, or identified through a specific federal state code within a country’s administrative or legal system.
-
D.
associatedWithStateCode
Indicates that an entity has a connection or linkage to a particular state identified by its state code.
-
E.
hasPrimaryStateJurisdiction
Indicates that a particular state has the main legal authority or responsibility to govern, regulate, or adjudicate matters concerning a given entity or situation.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5272ff53c8190ae7c399d49b585f5 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.