Triple
T27941961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Seed |
E700775
|
entity |
| Predicate | powersOrAbilities |
P42064
|
FINISHED |
| Object | control of plants |
—
|
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: control of plants | Statement: [El Seed, powersOrAbilities, control of plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powersOrAbilities Context triple: [El Seed, powersOrAbilities, control of plants]
-
A.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
B.
notableAbsorbedPowersFrom
Indicates that one entity is known for having taken in or acquired powers or abilities from another entity.
-
C.
hasSuperpower
chosen
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
D.
heroPower
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
E.
believedToHaveAbility
Indicates that one entity is thought or assumed to possess a particular capability or power, without asserting that the ability is actually verified.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 7:18 p.m.