Triple
T27397809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collinsport, Maine |
E691738
|
entity |
| Predicate | hasPrimaryFamily |
P91358
|
FINISHED |
| Object | Collins family |
—
|
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: Collins family | Statement: [Collinsport, Maine, hasPrimaryFamily, Collins family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryFamily Context triple: [Collinsport, Maine, hasPrimaryFamily, Collins family]
-
A.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
C.
hasCentralFamily
chosen
Indicates that an entity possesses or is organized around a primary or core family unit.
-
D.
hasRepresentativeFamily
Indicates that an entity is associated with a particular family that serves as its representative or characteristic example.
-
E.
hasPhysicalFamily
Indicates that one entity is related to another as a member of the same biological or legally recognized family.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 27, 2026, 12:28 p.m.