Triple
T38390509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motherworld |
E899702
|
entity |
| Predicate | hasHighRankingOfficer |
P199828
|
FINISHED |
| Object | Admiral Atticus Noble |
—
|
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: Admiral Atticus Noble | Statement: [Motherworld, hasHighRankingOfficer, Admiral Atticus Noble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighRankingOfficer Context triple: [Motherworld, hasHighRankingOfficer, Admiral Atticus Noble]
-
A.
hasGeneralOfficerRank
Indicates that an entity holds a military rank at the general officer level.
-
B.
isAboveOfficerGrade
Indicates that one entity holds a rank or position higher than an officer-grade level relative to another entity.
-
C.
isOfficerOf
Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
-
D.
isHighestRankedUniformedOfficerIn
Indicates that one entity holds the top-ranking position among all uniformed officers within a specified organization or jurisdiction.
-
E.
hasHighRankAssociatedWith
chosen
Indicates that one entity is associated with another entity that holds a high rank, status, or level within a given hierarchy or system.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 3, 2026, 4:31 p.m.