Triple
T1968966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cutlerite tradition |
E42752
|
entity |
| Predicate | hasLeaderLineage |
P33316
|
FINISHED |
| Object | leadership succession traced through Alpheus Cutler |
—
|
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: leadership succession traced through Alpheus Cutler | Statement: [Cutlerite tradition, hasLeaderLineage, leadership succession traced through Alpheus Cutler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeaderLineage Context triple: [Cutlerite tradition, hasLeaderLineage, leadership succession traced through Alpheus Cutler]
-
A.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
B.
hasMainTrunkLine
Indicates that an entity is connected to or served by a primary or central trunk line within a network or system.
-
C.
successorInLineage
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
D.
hasLeaderParticipant
Indicates that an entity participates in an event or activity in the role of a leader.
-
E.
hasTrailLength
Indicates that an entity (such as a trail or route) has a specific measured length.
- F. None of above. chosen
Provenance (4 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3d05cb88190963039d643bb6637 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb16a6db48190af04012e8ed2269f |
completed | March 7, 2026, 5:02 a.m. |
Created at: March 4, 2026, 7:36 p.m.