Triple
T10860426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Pembroke |
E256385
|
entity |
| Predicate | roleBeforeNavalService |
P96119
|
FINISHED |
| Object | merchant collier |
—
|
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: merchant collier | Statement: [Earl of Pembroke, roleBeforeNavalService, merchant collier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleBeforeNavalService Context triple: [Earl of Pembroke, roleBeforeNavalService, merchant collier]
-
A.
navyAfterUSService
Indicates that an individual served in a navy after completing service in the United States armed forces.
-
B.
militaryRankBeforeAccession
Indicates the military rank held by an individual prior to their accession to a particular office, position, or status.
-
C.
militaryRankEligibility
Indicates that one entity is qualified or permitted to hold, attain, or be considered for a specified military rank.
-
D.
enteredRoyalNavyFrontlineService
Indicates that an entity began active duty or operational deployment in the frontline forces of the Royal Navy.
-
E.
previousNavy
Indicates that one entity previously served in, belonged to, or was part of a navy before the current point in time.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75150ceb88190a70356d12ce130c5 |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:20 p.m.