Triple
T36785834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSEA Protector |
E908908
|
entity |
| Predicate | hasCaptainPortrayedBy |
P201252
|
FINISHED |
| Object | Tim Allen |
—
|
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: Tim Allen | Statement: [NSEA Protector, hasCaptainPortrayedBy, Tim Allen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaptainPortrayedBy Context triple: [NSEA Protector, hasCaptainPortrayedBy, Tim Allen]
-
A.
captainedByCharacter
Indicates that an entity (such as a ship, team, or group) is led or commanded by a specific character serving as its captain.
-
B.
hasNotableCaptain
Indicates that an entity has a specific captain who is recognized as notable or distinguished in some way.
-
C.
captainInName
Indicates that an entity’s name or title explicitly includes the word “Captain.”
-
D.
captainJackPortrayedBy
Indicates that one entity is the actor or performer who portrays the character Captain Jack.
-
E.
portrayedBySince
Indicates that an entity has been portrayed by a particular actor or performer starting from a specified point in time and continuing thereafter.
- F. None of above. chosen
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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
| PDg | Predicate description generation | batch_69ffe12d61e0819098692270ab2625e3 |
completed | May 10, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:12 p.m.