Triple
T4470258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A2C |
E98476
|
entity |
| Predicate | isSynchronousVariantOf |
P15288
|
FINISHED |
| Object | A3C |
—
|
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: A3C | Statement: [A2C, isSynchronousVariantOf, A3C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSynchronousVariantOf Context triple: [A2C, isSynchronousVariantOf, A3C]
-
A.
isAsynchronous
Indicates that the related process, operation, or interaction occurs without requiring simultaneous timing or immediate coordination between the involved entities.
-
B.
isSelfSynchronizing
Indicates that a process, system, or component can automatically align its timing or state with others without requiring external coordination or control.
-
C.
synchronizesWith
Indicates that two or more entities coordinate their states or activities so that they occur in step or remain temporally consistent with each other.
-
D.
isVersionOf
chosen
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
E.
isAbstractVersionOf
Indicates that one entity represents a conceptual, generalized, or non-concrete version of another, more specific or concrete 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.