Triple
T28114562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | II |
E710584
|
entity |
| Predicate | managedMainlyFor |
P56223
|
FINISHED |
| Object | ecosystem protection |
—
|
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: ecosystem protection | Statement: [II, managedMainlyFor, ecosystem protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedMainlyFor Context triple: [II, managedMainlyFor, ecosystem protection]
-
A.
primarilyFor
chosen
Indicates that something is mainly intended, designed, or used for a particular purpose, function, or beneficiary, even if it may have secondary uses.
-
B.
managedAct
Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
-
C.
managedUntil
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
-
D.
mainlyPerformed
Indicates that an action or activity is carried out primarily or predominantly by a particular entity compared to others.
-
E.
mannedLargelyBy
Indicates that one entity is primarily staffed, operated, or crewed by members of 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 9:13 p.m.