Triple
T2924667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computing Machinery and Intelligence |
E78813
|
entity |
| Predicate | proposesTestFor |
P20235
|
FINISHED |
| Object | machine intelligence |
—
|
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: machine intelligence | Statement: [Computing Machinery and Intelligence, proposesTestFor, machine intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesTestFor Context triple: [Computing Machinery and Intelligence, proposesTestFor, machine intelligence]
-
A.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
B.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
-
C.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
D.
establishesTest
chosen
Indicates that an entity creates or sets up a test or testing procedure for another entity.
-
E.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.