Triple
T30352512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gotta Lotta |
E772035
|
entity |
| Predicate | hookCharacteristic |
P274
|
FINISHED |
| Object | repetitive |
—
|
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: repetitive | Statement: [Gotta Lotta, hookCharacteristic, repetitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hookCharacteristic Context triple: [Gotta Lotta, hookCharacteristic, repetitive]
-
A.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
eraCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given historical or temporal era.
-
C.
maskCharacteristic
Indicates that one entity serves to conceal, obscure, or alter the apparent characteristics or properties of another entity.
-
D.
describesCharacteristicOf
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
-
E.
portCharacteristic
Indicates the specific properties or attributes that define how a port behaves or is configured in a given context.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823beafc81909d1cbfd11065be16 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.