Triple
T5849812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of the Orient |
E129999
|
entity |
| Predicate | includedPersonnelType |
P12729
|
FINISHED |
| Object | scientists |
—
|
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: scientists | Statement: [Army of the Orient, includedPersonnelType, scientists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedPersonnelType Context triple: [Army of the Orient, includedPersonnelType, scientists]
-
A.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
B.
personnelComposition
chosen
Indicates the makeup or distribution of people or roles within a group, organization, or unit.
-
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.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
E.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.