Triple
T12821593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milestone A |
E306541
|
entity |
| Predicate | typicalActivitiesAuthorized |
P75860
|
FINISHED |
| Object | technology demonstrations |
—
|
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: technology demonstrations | Statement: [Milestone A, typicalActivitiesAuthorized, technology demonstrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalActivitiesAuthorized Context triple: [Milestone A, typicalActivitiesAuthorized, technology demonstrations]
-
A.
permittedActivity
chosen
Indicates that a particular action or behavior is allowed or authorized within a given context or under specified rules.
-
B.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
C.
activitiesRestricted
Indicates that certain actions or behaviors are limited, prohibited, or constrained under specified conditions or for particular entities.
-
D.
settingOfActivities
Indicates that a particular place or context serves as the environment in which certain activities occur or are carried out.
-
E.
includesActivities
Indicates that one entity contains, encompasses, or has as part of it the activities associated with another entity.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9fcc8c8190a926ab0481d28f14 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:32 p.m.