Triple
T34040610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipping Point |
E872931
|
entity |
| Predicate | usesCounters |
P194487
|
FINISHED |
| Object | metal counters |
—
|
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: metal counters | Statement: [Tipping Point, usesCounters, metal counters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCounters Context triple: [Tipping Point, usesCounters, metal counters]
-
A.
usesCounterLength
Indicates that one entity determines or measures something based on the length of a counter value.
-
B.
areCountedBy
Indicates that one entity serves as the counting mechanism, record, or process by which the quantity of another entity is determined.
-
C.
usesCounterpoint
Indicates that one entity employs counterpoint, combining independent melodic lines in a structured, interdependent musical relationship with another.
-
D.
numberOfCounts
Indicates the total quantity or tally of discrete occurrences, items, or instances associated with an entity or event.
-
E.
count
Indicates the numerical quantity or total number of instances of a specified entity or event.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: May 1, 2026, 1:51 a.m.