Triple
T25642140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stack Overflow |
E642862
|
entity |
| Predicate | hasReputationSystem |
P180735
|
FINISHED |
| Object | points-based |
—
|
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: points-based | Statement: [Stack Overflow, hasReputationSystem, points-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReputationSystem Context triple: [Stack Overflow, hasReputationSystem, points-based]
-
A.
usesReputationSystem
chosen
Indicates that an entity employs a reputation-based mechanism to evaluate, rank, or make decisions about other entities or their actions.
-
B.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
C.
hasInUniverseReputation
Indicates that an entity holds a particular level or type of reputation within a specified fictional or conceptual universe.
-
D.
hasAwardReputation
Indicates that an entity is recognized or reputed for having received a particular award or set of awards.
-
E.
hasViewReputation
Indicates that an entity holds a reputation or recognized standing specifically related to viewing, observing, or accessing something.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 21, 2026, 5:45 p.m.