Triple
T973659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mounted Unit |
E21000
|
entity |
| Predicate | isDeployedDuring |
P11880
|
FINISHED |
| Object | parades |
—
|
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: parades | Statement: [Mounted Unit, isDeployedDuring, parades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDeployedDuring Context triple: [Mounted Unit, isDeployedDuring, parades]
-
A.
hasDeployment
Indicates that an entity is associated with or utilizes a specific deployment instance (e.g., of software, a model, or a system) in an operational context.
-
B.
deployedTo
Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
-
C.
deploymentTime
chosen
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
D.
laterDeployedIn
Indicates that one entity was deployed or put into operation in a particular context, location, or system at a later time than another.
-
E.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b45f28f081908d41b2d7f353708d |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a6aa2c8190aebba71320ab678f |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.