Triple
T28519925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E Block |
E721731
|
entity |
| Predicate | hasNotableGuard |
P170692
|
FINISHED |
| Object | Paul Edgecombe |
—
|
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: Paul Edgecombe | Statement: [E Block, hasNotableGuard, Paul Edgecombe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGuard Context triple: [E Block, hasNotableGuard, Paul Edgecombe]
-
A.
hasGuardForm
Indicates that an entity is in, or associated with, a specific guard or defensive stance/form.
-
B.
notableLocationGuarded
Indicates that a notable or significant location is being actively protected or guarded by an entity.
-
C.
hasGuardUnit
chosen
Indicates that an entity is protected or overseen by a specific guard unit.
-
D.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
E.
hasNotablePolicy
Indicates that an entity possesses a policy that is distinguished, significant, or otherwise noteworthy in its context.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: April 28, 2026, 3:20 a.m.