Triple
T27879603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis |
E705050
|
entity |
| Predicate | typicalMatchTypes |
P27263
|
FINISHED |
| Object | singles matches |
—
|
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: singles matches | Statement: [Genesis, typicalMatchTypes, singles matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMatchTypes Context triple: [Genesis, typicalMatchTypes, singles matches]
-
A.
typicalMatchType
chosen
Indicates the usual or most common type of match or pairing that characterizes how two entities are related or aligned.
-
B.
typicalMatchRules
Indicates that two entities are considered a standard or default match according to predefined matching rules or criteria.
-
C.
matchTypes
Indicates that two or more entities share the same type or category according to a specified classification.
-
D.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
E.
matchesType
Indicates that one entity has the same or a compatible type as another entity according to a defined type system or classification.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
Created at: April 27, 2026, 6:29 p.m.