Triple
T27908182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caitlin Moore |
E705845
|
entity |
| Predicate | relationshipToBoss |
P54286
|
FINISHED |
| Object | subordinate |
—
|
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: subordinate | Statement: [Caitlin Moore, relationshipToBoss, subordinate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToBoss Context triple: [Caitlin Moore, relationshipToBoss, subordinate]
-
A.
relationToExecutive
chosen
Indicates a relationship or connection that an entity has to an executive, such as reporting lines, oversight, or affiliation.
-
B.
relationshipToParent
Indicates the specific familial or social role an entity has in relation to its parent entity.
-
C.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
D.
relationshipToCaptain
Indicates the specific familial, professional, or social relationship that an entity has to a captain.
-
E.
rosterRelationship
Indicates a relationship where one entity is listed as a member, participant, or component within another entity’s roster or lineup.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: April 27, 2026, 6:47 p.m.