Triple
T36958373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvester |
E914244
|
entity |
| Predicate | isObjectiveBased |
P186808
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Harvester, isObjectiveBased, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isObjectiveBased Context triple: [Harvester, isObjectiveBased, true]
-
A.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
B.
USObjectives
Indicates that the relationship specifies the goals, aims, or strategic objectives pursued by the United States in a given context or situation.
-
C.
followsObjective
Indicates that one entity pursues, adheres to, or acts in accordance with the goal, plan, or objective defined by another entity.
-
D.
hasComplianceObjective
Indicates that an entity is associated with, or aims to fulfill, a specific compliance-related objective or requirement.
-
E.
formatObjective
Indicates that an entity specifies or defines the desired formatting style or structure to be achieved for another entity or output.
- F. None of above. chosen
Provenance (4 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.