Triple
T7796733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Aviation Training Support Group 23 |
E180316
|
entity |
| Predicate | supportsServiceMembers |
P41839
|
FINISHED |
| Object | Marine officers |
—
|
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: Marine officers | Statement: [Marine Aviation Training Support Group 23, supportsServiceMembers, Marine officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsServiceMembers Context triple: [Marine Aviation Training Support Group 23, supportsServiceMembers, Marine officers]
-
A.
servesMember
Indicates that one entity provides services or assistance to another entity that is considered its member.
-
B.
membersServe
Indicates that the members of a group perform services or duties for, or on behalf of, another entity or organization.
-
C.
hasSupportService
chosen
Indicates that one entity provides or is associated with a support-related service for another entity.
-
D.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
E.
supportsTeam
Indicates that one entity provides backing, assistance, or endorsement to a particular team.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:32 p.m.