Triple
T187496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMP |
E4013
|
entity |
| Predicate | managementFunction |
P4839
|
FINISHED |
| Object | remote monitoring of ARPANET links |
—
|
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: remote monitoring of ARPANET links | Statement: [IMP, managementFunction, remote monitoring of ARPANET links]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementFunction Context triple: [IMP, managementFunction, remote monitoring of ARPANET links]
-
A.
manager
Indicates that one entity holds a supervisory or administrative role with authority and responsibility over another entity.
-
B.
managementApproach
chosen
Indicates the strategy, methods, or style used to direct, organize, and oversee the activities or resources of an entity or process.
-
C.
committeeFunction
Indicates that a committee performs, is responsible for, or is associated with a particular function or role.
-
D.
managedTeam
Indicates that one entity had responsibility for directing, supervising, and coordinating the work of another group or team.
-
E.
governmentalFunction
Indicates that an entity performs, embodies, or is responsible for an official role, duty, or activity of a government.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594940e48190a3d8efbce46241c3 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25670feb081908e26a2543ebe7b3a |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.