Triple
T20885014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abella |
E514254
|
entity |
| Predicate | canReasonAbout |
P142240
|
FINISHED |
| Object | lambda-calculus |
—
|
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: lambda-calculus | Statement: [Abella, canReasonAbout, lambda-calculus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReasonAbout Context triple: [Abella, canReasonAbout, lambda-calculus]
-
A.
reasoningType
Indicates the specific kind or mode of reasoning applied in deriving a conclusion or making an inference between entities.
-
B.
canBeThoughtBy
Indicates that something is capable of being conceived, imagined, or mentally represented by a thinking entity.
-
C.
canDetermine
Indicates that one entity has the ability or authority to find out, establish, or decide the state, value, or outcome of another entity or situation.
-
D.
hasAutonomyReason
Indicates that an entity has a specific reason or justification for its autonomy or independent decision-making.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67c9d1c81908031eb77c124f119 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:46 p.m.