Triple
T30605386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finn McMissile |
E779026
|
entity |
| Predicate | isSpyFor |
P28504
|
FINISHED |
| Object | British Intelligence |
—
|
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: British Intelligence | Statement: [Finn McMissile, isSpyFor, British Intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpyFor Context triple: [Finn McMissile, isSpyFor, British Intelligence]
-
A.
isSpyAircraft
Indicates that an aircraft is designed or used primarily for espionage, reconnaissance, or intelligence-gathering activities.
-
B.
hasSpyProtagonist
Indicates that the main character in the work is a spy or primarily engaged in espionage activities.
-
C.
spiedFor
chosen
Indicates that one entity secretly gathered and provided information on behalf of another entity, typically an intelligence service or organization.
-
D.
spiedOn
Indicates that one entity secretly observed or gathered information about another entity without their knowledge or consent.
-
E.
isSpurOf
Indicates that one entity is a secondary offshoot, branch, or derivative extension originating from another primary entity.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b5450c8190bb5152b6e3dd6536 |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:25 p.m.