Triple
T37729872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abraham Cornelius |
E940125
|
entity |
| Predicate | roleInWeaponX |
P203956
|
FINISHED |
| Object | lead scientist |
—
|
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: lead scientist | Statement: [Abraham Cornelius, roleInWeaponX, lead scientist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWeaponX Context triple: [Abraham Cornelius, roleInWeaponX, lead scientist]
-
A.
associatedWithWeapon
Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given context.
-
B.
wielderRole
Indicates the specific role or function an entity has in relation to the item or power it wields.
-
C.
titleCharacterWeapon
Indicates that a weapon is the primary or signature armament associated with a story’s title character.
-
D.
roleInCombatSystem
Indicates the specific function or responsibility an entity has within a combat or battle mechanics framework.
-
E.
designerOfWeaponUsed
Indicates that one entity is the designer or creator of a weapon that was used by another entity in some event or action.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02ff7de1d881909c29729f2a771381 |
completed | May 12, 2026, 10:22 a.m. |
| PD | Predicate disambiguation | batch_6a02fd1c45c48190bf9dbd91acaeee9f |
completed | May 12, 2026, 10:12 a.m. |
| PDg | Predicate description generation | batch_6a02ff7d041c81909854fc5025171e94 |
completed | May 12, 2026, 10:22 a.m. |
Created at: May 3, 2026, 4:18 p.m.