Triple
T28814168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perofascia |
E727593
|
entity |
| Predicate | notAB |
P203487
|
FINISHED |
| Object | true fungus |
—
|
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: true fungus | Statement: [Perofascia, notAB, true fungus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAB Context triple: [Perofascia, notAB, true fungus]
-
A.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
B.
notTypically
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
-
C.
notStatus
Indicates that an entity does not have, is not in, or does not match a specified status or state.
-
D.
notANumber
Indicates that a given value does not represent a valid numeric quantity.
-
E.
notStandardized
Indicates that the referenced item, process, or representation does not conform to an established standard or agreed-upon specification.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a019037edbc8190bdaec436ac2fcec6 |
completed | May 11, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_6a018fe05a34819080068f588b5ff80c |
completed | May 11, 2026, 8:14 a.m. |
| PDg | Predicate description generation | batch_6a0190370290819096183e9fb7d32cff |
completed | May 11, 2026, 8:15 a.m. |
Created at: April 28, 2026, 6:32 a.m.