Triple
T7648122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexandrov compactification |
E173177
|
entity |
| Predicate | outputProperty |
P77812
|
FINISHED |
| Object | compactness |
—
|
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: compactness | Statement: [Alexandrov compactification, outputProperty, compactness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputProperty Context triple: [Alexandrov compactification, outputProperty, compactness]
-
A.
outputOf
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
B.
outputConfiguration
Indicates how the results or data produced by a process, system, or component are structured, formatted, or directed to their destination.
-
C.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced by another entity or process.
-
D.
outputFunction
Indicates that one entity serves as the function or procedure responsible for producing or returning the output of another entity or process.
-
E.
outputUsedBy
Indicates that a particular output produced by one entity is consumed, referenced, or otherwise utilized by another entity.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c6faf6328c8190bce0a3f8a17ef890 |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e9ef1c81909c8bff716541ac1f |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8195e5c8190835e28d44e19f6ef |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:58 p.m.