Triple
T38226858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaygee |
E1012167
|
entity |
| Predicate | rankSeniorityRelativeTo |
P161031
|
FINISHED |
| Object | below Lieutenant |
—
|
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: below Lieutenant | Statement: [Jaygee, rankSeniorityRelativeTo, below Lieutenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankSeniorityRelativeTo Context triple: [Jaygee, rankSeniorityRelativeTo, below Lieutenant]
-
A.
rankWithinOrganization
Indicates the relative hierarchical position or level an entity holds within a specific organization.
-
B.
denotesSeniority
chosen
Indicates that one entity holds a higher rank, status, or level of seniority relative to another entity.
-
C.
seniorRank
Indicates that one entity holds a higher or more senior rank or position than another entity.
-
D.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
E.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.