Triple
T18044154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fama–French three-factor model |
E431728
|
entity |
| Predicate | factorName |
P744
|
FINISHED |
| Object | market factor |
—
|
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: market factor | Statement: [Fama–French three-factor model, factorName, market factor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factorName Context triple: [Fama–French three-factor model, factorName, market factor]
-
A.
featuresFamilyName
Indicates that an entity is associated with or displays a particular family name.
-
B.
nameOf
chosen
Indicates that one entity is the name or designation of another entity.
-
C.
forceName
Indicates that a specific name or label is being imposed or enforced on an entity, overriding any existing or default naming.
-
D.
namedAs
Indicates that one entity is given, known by, or referred to using the name of another entity.
-
E.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff13f488190993445769551c9c2 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.