Triple
T32594118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trần clan |
E833150
|
entity |
| Predicate | originActivity |
P18207
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [Trần clan, originActivity, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originActivity Context triple: [Trần clan, originActivity, fishing]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
originSite
Indicates the place or site from which something or someone originally comes or is derived.
-
C.
originContext
chosen
Indicates the situational or environmental circumstances from which an entity, event, or piece of information originates.
-
D.
originAssociatedWith
Indicates a relationship where an entity is connected to, derived from, or influenced by a particular origin, source, or point of beginning.
-
E.
originUse
Indicates that one entity is used as the original source, basis, or starting point for the creation, derivation, or use of 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01bb06422c819095bb42f6f3a0e801 |
completed | May 11, 2026, 11:18 a.m. |
| PD | Predicate disambiguation | batch_6a01b9991c348190ac49b65ea2fd86ed |
completed | May 11, 2026, 11:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.