Triple
T4410328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alderson disk |
E94836
|
entity |
| Predicate | hasPotentialUse |
P20795
|
FINISHED |
| Object | supporting extremely large populations |
—
|
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: supporting extremely large populations | Statement: [Alderson disk, hasPotentialUse, supporting extremely large populations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPotentialUse Context triple: [Alderson disk, hasPotentialUse, supporting extremely large populations]
-
A.
hasResourcePotential
chosen
Indicates that an entity possesses the capacity or suitability to provide, generate, or support a particular resource in the future.
-
B.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
D.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
E.
isPotentiallyActive
Indicates that an entity has the capacity or conditions to become active, but is not necessarily active at the present moment.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e4c58c8190b4190aad3095a1dd |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.