Triple
T63207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Research and Development Board |
E1254
|
entity |
| Predicate | hasTask |
P1410
|
FINISHED |
| Object | integration of service research programs |
—
|
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: integration of service research programs | Statement: [Research and Development Board, hasTask, integration of service research programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTask Context triple: [Research and Development Board, hasTask, integration of service research programs]
-
A.
hasMissionActivity
Indicates that an entity is associated with, performs, or is involved in a specific mission-related activity.
-
B.
hasProcess
chosen
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
C.
hasWorkInCollection
Indicates that a work or item is included as part of a particular collection.
-
D.
hasCurrent
Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
-
E.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.