Triple
T19700068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-10 parachute |
E473066
|
entity |
| Predicate | userActivity |
P100358
|
FINISHED |
| Object | tactical airborne assault |
—
|
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: tactical airborne assault | Statement: [D-10 parachute, userActivity, tactical airborne assault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userActivity Context triple: [D-10 parachute, userActivity, tactical airborne assault]
-
A.
targetUserActivity
Indicates that a specific user is the intended recipient or focus of a particular activity or action.
-
B.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
C.
playerActivities
chosen
Indicates the various actions, events, or engagements that a player participates in within a given context or system.
-
D.
evidenceOfActivity
Indicates that there is information or data supporting the occurrence or performance of a particular activity or action.
-
E.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b4e01081908f857f219d5d7a24 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.