Triple
T25723257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USPHS O-7 |
E645045
|
entity |
| Predicate | isLineOrStaff |
P159493
|
FINISHED |
| Object | staff corps–type rank |
—
|
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: staff corps–type rank | Statement: [USPHS O-7, isLineOrStaff, staff corps–type rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLineOrStaff Context triple: [USPHS O-7, isLineOrStaff, staff corps–type rank]
-
A.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
B.
usesInterpretiveStaff
Indicates that an entity relies on interpretive staff (such as guides, educators, or docents) to convey information, context, or explanations about something to an audience.
-
C.
partOfBandLineup
Indicates that an entity is a member of, or included in, the lineup of a particular band.
-
D.
numberOfStaves
Indicates the quantity of staves associated with or contained in a given entity.
-
E.
isBusyLine
Indicates that a communication line or channel is currently in use and cannot accept additional connections or calls.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc683cd48190bf4bab9cb8de691a |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 10:07 p.m.