Triple
T10860395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Pembroke |
E256385
|
entity |
| Predicate | refittedFor |
P1510
|
FINISHED |
| Object | voyage of exploration |
—
|
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: voyage of exploration | Statement: [Earl of Pembroke, refittedFor, voyage of exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refittedFor Context triple: [Earl of Pembroke, refittedFor, voyage of exploration]
-
A.
refit
Indicates that an existing object or structure is being modified, repaired, or equipped with new parts or features to restore or improve its function.
-
B.
armamentAfterRefit
Indicates that the armament of an entity reflects its configuration after undergoing a refit or upgrade.
-
C.
typeAfterRefit
Indicates that an entity’s type or classification after undergoing a refit or modification is the specified value.
-
D.
rebuiltFor
chosen
Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
-
E.
refurbishedIn
Indicates that an entity has undergone restoration, repair, or renovation at a specific time or during a particular period.
- 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_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. |
Created at: April 8, 2026, 9:20 p.m.