Triple
T7325991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA blocks leader |
E168875
|
entity |
| Predicate | positionMostCommon |
P72600
|
FINISHED |
| Object | center |
—
|
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: center | Statement: [NBA blocks leader, positionMostCommon, center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionMostCommon Context triple: [NBA blocks leader, positionMostCommon, center]
-
A.
moreCommonIn
Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
-
B.
moreCommonAs
chosen
Indicates that one thing occurs or is observed more frequently in a specified role, form, or context than in another.
-
C.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
largestConcentrationIn
Indicates that something has its highest density, amount, or presence within a specified location or group compared to all other locations or groups.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a612c08190b7a3fefa811bbcec |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.