Triple
T23044528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caleb Strong |
E573839
|
entity |
| Predicate | isInTheCategory |
P15481
|
FINISHED |
| Object | Governors of Massachusetts |
—
|
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: Governors of Massachusetts | Statement: [Caleb Strong, isInTheCategory, Governors of Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInTheCategory Context triple: [Caleb Strong, isInTheCategory, Governors of Massachusetts]
-
A.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
-
B.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
-
C.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
D.
hasInGameCategory
Indicates that an in-game item, action, or entity belongs to a specific predefined category within the game’s classification system.
-
E.
hasEnlistedCategory
Indicates that an entity is associated with a specific enlisted classification or category within an organization or system.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1851811e08190a5af6a112687327e |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.