Triple
T34057371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Jack’s Stronghold |
E873397
|
entity |
| Predicate | primaryDefensiveStrongholdOf |
P77480
|
FINISHED |
| Object | Captain Jack |
E249977
|
NE 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: Captain Jack | Statement: [Captain Jack’s Stronghold, primaryDefensiveStrongholdOf, Captain Jack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDefensiveStrongholdOf Context triple: [Captain Jack’s Stronghold, primaryDefensiveStrongholdOf, Captain Jack]
-
A.
strongholdOf
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
B.
primaryStronghold
chosen
Indicates that one location serves as the main base, fortress, or central stronghold for an entity compared to its other sites.
-
C.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
D.
primaryDefendedCity
Indicates that an entity served as the main or principal city that another entity was responsible for defending.
-
E.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
- F. None of above.
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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36a0444fb08190ac3f70aad32d8e4d |
completed | June 20, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.