Triple
T38568685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rifle Company C |
E928299
|
entity |
| Predicate | standardPersonnel |
P195262
|
FINISHED |
| Object | infantry Marines |
—
|
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: infantry Marines | Statement: [Rifle Company C, standardPersonnel, infantry Marines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardPersonnel Context triple: [Rifle Company C, standardPersonnel, infantry Marines]
-
A.
personnel
Indicates that an entity serves as staff or workforce associated with another entity, such as an organization, project, or facility.
-
B.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
C.
authorizedPersonnel
Indicates that the referenced entity is officially permitted or empowered to access, use, or perform actions within a specified system, resource, or context.
-
D.
peakPersonnel
Indicates the maximum number of personnel involved or present at any point during a specified period or activity.
-
E.
usedPersonnel
Indicates that certain personnel are employed, engaged, or utilized in performing a particular activity, task, or operation.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: May 3, 2026, 4:32 p.m.