Triple
T733680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack |
E14882
|
entity |
| Predicate | hasFrequencyType |
P7407
|
FINISHED |
| Object | very common name |
—
|
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: very common name | Statement: [Jack, hasFrequencyType, very common name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrequencyType Context triple: [Jack, hasFrequencyType, very common name]
-
A.
hasRateType
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
-
B.
tienePeriodicidad
chosen
Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
-
C.
hasMonthType
Indicates that something is associated with, classified by, or characterized as a particular type or category of month.
-
D.
frequencyRequirement
Indicates a constraint specifying how often an action, event, or condition must occur within a given context or time frame.
-
E.
hasYearType
Indicates a relationship where an entity is associated with a specific classification or category of year (such as calendar, fiscal, academic, or other year type).
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fafee081909bf356854c09aaff |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.