Triple
T20697867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo superior |
E508701
|
entity |
| Predicate | typicalOnsetOfPowers |
P141138
|
FINISHED |
| Object | puberty |
—
|
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: puberty | Statement: [Homo superior, typicalOnsetOfPowers, puberty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOnsetOfPowers Context triple: [Homo superior, typicalOnsetOfPowers, puberty]
-
A.
typicalPower
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
-
B.
typeOfPowerGranted
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
C.
notableAbsorbedPowersFrom
Indicates that one entity is known for having taken in or acquired powers or abilities from another entity.
-
D.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
-
E.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c1132178819081086e085f7b3ff8 |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:11 p.m.