Triple
T34011915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirate Lords |
E872136
|
entity |
| Predicate | eachMemberHolds |
P80161
|
FINISHED |
| Object | Piece of Eight |
—
|
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: Piece of Eight | Statement: [Pirate Lords, eachMemberHolds, Piece of Eight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eachMemberHolds Context triple: [Pirate Lords, eachMemberHolds, Piece of Eight]
-
A.
eachMemberHas
chosen
Indicates that every individual element within a group or collection possesses or is associated with a specified property, attribute, or item.
-
B.
heldByMembersOf
Indicates that something is possessed, controlled, or owned collectively by the members of a specified group or organization.
-
C.
allMembersAre
Indicates that every member of a specified group or set satisfies a given condition or belongs entirely to another specified group.
-
D.
heldEvery
Indicates that an entity consistently possessed or maintained control of another entity throughout every instance or period within a specified range.
-
E.
hasMemberFromEach
Indicates that a group or collection includes at least one member originating from each specified category, set, or subgroup.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.